Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9df4ca78d0999aae9939c8684ad9380b587fd53f5da9c2d66f71968adc290d

Tx prefix hash: 47de1077933694a079e09e58413aee60e8b6feeb167a3763d7846913d562182f
Tx public key: 0e815dde1dd2eb4d42f987eae613a4e24e35bb807ba3616bcc2c8794c9383be3
Timestamp: 1711881204 Timestamp [UCT]: 2024-03-31 10:33:24 Age [y:d:h:m:s]: 01:224:14:10:26
Block: 990266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419180 RingCT/type: yes/0
Extra: 010e815dde1dd2eb4d42f987eae613a4e24e35bb807ba3616bcc2c8794c9383be302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d974bf30ee7cdf6f2f7071214cc51a4470a93da8287271c3557e9ebda8caa1 0.600000000000 1450588 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": 990276, "vin": [ { "gen": { "height": 990266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d974bf30ee7cdf6f2f7071214cc51a4470a93da8287271c3557e9ebda8caa1" } } ], "extra": [ 1, 14, 129, 93, 222, 29, 210, 235, 77, 66, 249, 135, 234, 230, 19, 164, 226, 78, 53, 187, 128, 123, 163, 97, 107, 204, 44, 135, 148, 201, 56, 59, 227, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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