Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17e413acf4ab8e7047397024eb0fed6a2decb42d269f882afa5ae9bd3c70123

Tx prefix hash: fbdbce32e299464ad7e6c0b658eaae82bd55402ef825f36ec9fd58ebc271383c
Tx public key: 5ce662a418d4c9d9f911a9331fabe275f8973e463245aab77bbc0c01923f46f1
Timestamp: 1722171598 Timestamp [UCT]: 2024-07-28 12:59:58 Age [y:d:h:m:s]: 01:185:13:56:40
Block: 1075556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391068 RingCT/type: yes/0
Extra: 015ce662a418d4c9d9f911a9331fabe275f8973e463245aab77bbc0c01923f46f1021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab55ececf803eca5dadf30ec91bbd9297ddfe5f38e3ba5fb97415c1fdd1aa658 0.600000000000 1548085 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": 1075566, "vin": [ { "gen": { "height": 1075556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab55ececf803eca5dadf30ec91bbd9297ddfe5f38e3ba5fb97415c1fdd1aa658" } } ], "extra": [ 1, 92, 230, 98, 164, 24, 212, 201, 217, 249, 17, 169, 51, 31, 171, 226, 117, 248, 151, 62, 70, 50, 69, 170, 183, 123, 188, 12, 1, 146, 63, 70, 241, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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