Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d90d306e37a972539fd8a7536843944b593baf8cd9abdbaf89ba8bcd84feb7

Tx prefix hash: 9440136ba45007a5ea1be786d9cf417e96dcd9386f02fe87e01bcdc0602716eb
Tx public key: 6a35a465d66bfe7f63eeb49bec3c67553964cb3965d3aa068bf0377d683971e6
Timestamp: 1698636105 Timestamp [UCT]: 2023-10-30 03:21:45 Age [y:d:h:m:s]: 01:139:08:48:32
Block: 880652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360612 RingCT/type: yes/0
Extra: 016a35a465d66bfe7f63eeb49bec3c67553964cb3965d3aa068bf0377d683971e6021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.741368893000 dcy

stealth address amount amount idx
00: 299c8d92427beaf4a670dacb5138dc3b0536ea208130f98dcb1924f9395c5052 0.741368893000 1336216 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": 880662, "vin": [ { "gen": { "height": 880652 } } ], "vout": [ { "amount": 741368893, "target": { "key": "299c8d92427beaf4a670dacb5138dc3b0536ea208130f98dcb1924f9395c5052" } } ], "extra": [ 1, 106, 53, 164, 101, 214, 107, 254, 127, 99, 238, 180, 155, 236, 60, 103, 85, 57, 100, 203, 57, 101, 211, 170, 6, 139, 240, 55, 125, 104, 57, 113, 230, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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