Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f294efffe19b4fcd0e270be14b3d4126f667da916b46a069e8429f02969deb6

Tx prefix hash: 8d4df5990d851aa5df12a290fae0ffefb397a12a8a451403afc31c8a12a5ab18
Tx public key: 52fb45b5ca103684beb318ccf131d46a49ac995d7d79f2ad21f03a843c17784a
Timestamp: 1727644074 Timestamp [UCT]: 2024-09-29 21:07:54 Age [y:d:h:m:s]: 00:104:08:02:59
Block: 1120927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74591 RingCT/type: yes/0
Extra: 0152fb45b5ca103684beb318ccf131d46a49ac995d7d79f2ad21f03a843c17784a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 407e5dc2c961e84edf170cf2cfced114323299b25cfbfb9efe0439a89e75d074 0.600000000000 1603018 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": 1120937, "vin": [ { "gen": { "height": 1120927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "407e5dc2c961e84edf170cf2cfced114323299b25cfbfb9efe0439a89e75d074" } } ], "extra": [ 1, 82, 251, 69, 181, 202, 16, 54, 132, 190, 179, 24, 204, 241, 49, 212, 106, 73, 172, 153, 93, 125, 121, 242, 173, 33, 240, 58, 132, 60, 23, 120, 74, 2, 17, 0, 0, 0, 3, 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