Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2370b6f72c0ac2d4a46cee239dfd62d1417e8a0fd6b4b01e35d516d37d266b5f

Tx prefix hash: d6c4c009e8cb413be545677df4f7e18f22aae396318d7d2cf3ef320adf9acd2b
Tx public key: 56b1c40efc2c179c64270b32da0f5a1c32547cf128583464b3242ae996165009
Timestamp: 1577207312 Timestamp [UCT]: 2019-12-24 17:08:32 Age [y:d:h:m:s]: 04:344:03:37:52
Block: 30906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135042 RingCT/type: yes/0
Extra: 0156b1c40efc2c179c64270b32da0f5a1c32547cf128583464b3242ae9961650090211000000044ac5aa02000000000000000000

1 output(s) for total of 484.837779189000 dcy

stealth address amount amount idx
00: 3523f9846a3f7ebe75b6f830533f994aa40caf7101d0f0032fa2c09647d2e195 484.837779189000 51014 of 0

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": 30916, "vin": [ { "gen": { "height": 30906 } } ], "vout": [ { "amount": 484837779189, "target": { "key": "3523f9846a3f7ebe75b6f830533f994aa40caf7101d0f0032fa2c09647d2e195" } } ], "extra": [ 1, 86, 177, 196, 14, 252, 44, 23, 156, 100, 39, 11, 50, 218, 15, 90, 28, 50, 84, 124, 241, 40, 88, 52, 100, 179, 36, 42, 233, 150, 22, 80, 9, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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