Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b7f2be7b459bf0cc75c97f34e07f6e0a99464e85a56971cf73cd9dd170b688

Tx prefix hash: 2db9523b82c4ca45e99f5e4b2430052bfbcab29d5a41b91586a739d4bed85933
Tx public key: 20b0bad4a091c055909d822b76e8b1896b2db01770304d8a88fffb1041c3c752
Timestamp: 1685451625 Timestamp [UCT]: 2023-05-30 13:00:25 Age [y:d:h:m:s]: 01:275:03:09:20
Block: 771381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457810 RingCT/type: yes/0
Extra: 0120b0bad4a091c055909d822b76e8b1896b2db01770304d8a88fffb1041c3c75202110000000475e3f0e9000000000000000000

1 output(s) for total of 1.706454462000 dcy

stealth address amount amount idx
00: 536e9fbf43f504ff5f3d7c7896671f67e76802c502dacd85741cee810bfb485d 1.706454462000 1220744 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": 771391, "vin": [ { "gen": { "height": 771381 } } ], "vout": [ { "amount": 1706454462, "target": { "key": "536e9fbf43f504ff5f3d7c7896671f67e76802c502dacd85741cee810bfb485d" } } ], "extra": [ 1, 32, 176, 186, 212, 160, 145, 192, 85, 144, 157, 130, 43, 118, 232, 177, 137, 107, 45, 176, 23, 112, 48, 77, 138, 136, 255, 251, 16, 65, 195, 199, 82, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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