Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2ab5cf3c5d256b6d137565233c00921db548f325d4dc58186775a4c5d6cedb

Tx prefix hash: bbfef09fb58f1874e043910a8425d111c1c43cd6147b4e22babf2422bb3463db
Tx public key: ad0ea70754e74992557231f6a9e503a7a646478c45a4ff53b577937833bf1868
Timestamp: 1729214713 Timestamp [UCT]: 2024-10-18 01:25:13 Age [y:d:h:m:s]: 00:095:23:57:48
Block: 1133957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68562 RingCT/type: yes/0
Extra: 01ad0ea70754e74992557231f6a9e503a7a646478c45a4ff53b577937833bf1868021100000003007f978a000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: debcb9b8b15b5e4ca9bca15df89d1c15df68e324d074bca32b21117f10c0def4 0.600010000000 1617182 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": 1133967, "vin": [ { "gen": { "height": 1133957 } } ], "vout": [ { "amount": 600010000, "target": { "key": "debcb9b8b15b5e4ca9bca15df89d1c15df68e324d074bca32b21117f10c0def4" } } ], "extra": [ 1, 173, 14, 167, 7, 84, 231, 73, 146, 85, 114, 49, 246, 169, 229, 3, 167, 166, 70, 71, 140, 69, 164, 255, 83, 181, 119, 147, 120, 51, 191, 24, 104, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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