Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dfe787bd66d634f23e3b1c9925f8a9f222ebf23f091152524546bc52ab8f25b

Tx prefix hash: 68589cf2f4e757abc9e274a722d562b22d9c54a0107a450ea621a2d97fd4a812
Tx public key: b9be7c6bb0ed88370dc9be92e081dd5e1003f2886a23f143b84d2d98bfebf0c6
Timestamp: 1583538632 Timestamp [UCT]: 2020-03-06 23:50:32 Age [y:d:h:m:s]: 04:254:13:44:13
Block: 77896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076375 RingCT/type: yes/0
Extra: 01b9be7c6bb0ed88370dc9be92e081dd5e1003f2886a23f143b84d2d98bfebf0c602110000001d4ac5aa02000000000000000000

1 output(s) for total of 338.765370246000 dcy

stealth address amount amount idx
00: 00ead84b6afaf935dcfe50ccb236a85766fd51f672a0c6d288f811f1bb6e4713 338.765370246000 143139 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": 77906, "vin": [ { "gen": { "height": 77896 } } ], "vout": [ { "amount": 338765370246, "target": { "key": "00ead84b6afaf935dcfe50ccb236a85766fd51f672a0c6d288f811f1bb6e4713" } } ], "extra": [ 1, 185, 190, 124, 107, 176, 237, 136, 55, 13, 201, 190, 146, 224, 129, 221, 94, 16, 3, 242, 136, 106, 35, 241, 67, 184, 77, 45, 152, 191, 235, 240, 198, 2, 17, 0, 0, 0, 29, 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