Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e368b9db6e630865e6876b24adf0757c52fdbddb8f19eab427c52c6ff59274

Tx prefix hash: 80d8bc9ab7a8b9716e467d2e4411acb956760e5ec6a2abe92bd3e82efd86145a
Tx public key: e221705a2f3d5f2842acf2ad4f1df73fdf896c30ab008d5ca18485b347c836ec
Timestamp: 1709269670 Timestamp [UCT]: 2024-03-01 05:07:50 Age [y:d:h:m:s]: 00:332:01:22:16
Block: 968603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237453 RingCT/type: yes/0
Extra: 01e221705a2f3d5f2842acf2ad4f1df73fdf896c30ab008d5ca18485b347c836ec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a244a14329883c78bd2c33774e3919004d9cf77ebc34f11ee5f55c3100d7dbe6 0.600000000000 1428420 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": 968613, "vin": [ { "gen": { "height": 968603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a244a14329883c78bd2c33774e3919004d9cf77ebc34f11ee5f55c3100d7dbe6" } } ], "extra": [ 1, 226, 33, 112, 90, 47, 61, 95, 40, 66, 172, 242, 173, 79, 29, 247, 63, 223, 137, 108, 48, 171, 0, 141, 92, 161, 132, 133, 179, 71, 200, 54, 236, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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