Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f41bb0de6bf07e9d588aa693791f5d1a178c03641ddfbc093d20517ff13261ac

Tx prefix hash: 4c70b78a55c9f30e56a3a3ccec5b0adb88886d7c3ebff5d22662744a8d99deab
Tx public key: 95e4a00a21cfd50e23053d365df5b3ab617b5d8d170ab03aa4ed506d7afe58c2
Timestamp: 1695439757 Timestamp [UCT]: 2023-09-23 03:29:17 Age [y:d:h:m:s]: 01:176:09:11:33
Block: 854136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387138 RingCT/type: yes/0
Extra: 0195e4a00a21cfd50e23053d365df5b3ab617b5d8d170ab03aa4ed506d7afe58c202110000001e4b8f5122000000000000000000

1 output(s) for total of 0.907596712000 dcy

stealth address amount amount idx
00: f7247c0fe2cc9baf5920f62641d0faf375c9f97170d9267c02747e7a5b4f3630 0.907596712000 1308090 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": 854146, "vin": [ { "gen": { "height": 854136 } } ], "vout": [ { "amount": 907596712, "target": { "key": "f7247c0fe2cc9baf5920f62641d0faf375c9f97170d9267c02747e7a5b4f3630" } } ], "extra": [ 1, 149, 228, 160, 10, 33, 207, 213, 14, 35, 5, 61, 54, 93, 245, 179, 171, 97, 123, 93, 141, 23, 10, 176, 58, 164, 237, 80, 109, 122, 254, 88, 194, 2, 17, 0, 0, 0, 30, 75, 143, 81, 34, 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