Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a38288fd28b6e33346e31694eaae08537224c463d4b516cb230973e055951c2f

Tx prefix hash: 1ed876715034192b4e18e8fc270ac84099dc3be68f5e2220d559aa4d07fe028f
Tx public key: b0e9e506857b6918213d33ac3e53aa0157c54c8757f8a40b1454caadd3545259
Timestamp: 1704328456 Timestamp [UCT]: 2024-01-04 00:34:16 Age [y:d:h:m:s]: 01:310:18:20:30
Block: 927641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480914 RingCT/type: yes/0
Extra: 01b0e9e506857b6918213d33ac3e53aa0157c54c8757f8a40b1454caadd35452590211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8efca9539fe15c1b0c15363081e008a28493737614434994fe1a9281930ed74 0.600000000000 1385477 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 927651, "vin": [ { "gen": { "height": 927641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8efca9539fe15c1b0c15363081e008a28493737614434994fe1a9281930ed74" } } ], "extra": [ 1, 176, 233, 229, 6, 133, 123, 105, 24, 33, 61, 51, 172, 62, 83, 170, 1, 87, 197, 76, 135, 87, 248, 164, 11, 20, 84, 202, 173, 211, 84, 82, 89, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8