Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce1d647a1c5212ae0680b03eb65b4fb80d1bf12798054f313c67db4f1f9a71d3

Tx prefix hash: 159956907c07f7c7c26beff0199aef46eebe5cc21c2aa8a628b46b584bb6b290
Tx public key: 34d263ebc7027311cf2f13540a239df35b7917c165e5a6ee134893695f1fc9ce
Timestamp: 1715212993 Timestamp [UCT]: 2024-05-09 00:03:13 Age [y:d:h:m:s]: 00:243:10:06:30
Block: 1017871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174224 RingCT/type: yes/0
Extra: 0134d263ebc7027311cf2f13540a239df35b7917c165e5a6ee134893695f1fc9ce0211000000130011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b066a07610ea57fa872bb9290ab9a5bc1bc54a3c647806a1a0f8af15c1710dc 0.600000000000 1481656 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": 1017881, "vin": [ { "gen": { "height": 1017871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b066a07610ea57fa872bb9290ab9a5bc1bc54a3c647806a1a0f8af15c1710dc" } } ], "extra": [ 1, 52, 210, 99, 235, 199, 2, 115, 17, 207, 47, 19, 84, 10, 35, 157, 243, 91, 121, 23, 193, 101, 229, 166, 238, 19, 72, 147, 105, 95, 31, 201, 206, 2, 17, 0, 0, 0, 19, 0, 17, 5, 91, 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