Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d95d871901b337e5a36bb2cfdc5d9a8afa47b3dc713d551187463930b2947a

Tx prefix hash: e1a6eb8634a7322c5a76f7d740bf76ea3f8d04ab3d31763166fd9ee4f33fa572
Tx public key: 903cc45ecc21dc8fa9f006f41d092153ddca5e1ebf09689520655a31dd0b3dc6
Timestamp: 1727407869 Timestamp [UCT]: 2024-09-27 03:31:09 Age [y:d:h:m:s]: 00:218:05:09:21
Block: 1118970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155788 RingCT/type: yes/0
Extra: 01903cc45ecc21dc8fa9f006f41d092153ddca5e1ebf09689520655a31dd0b3dc6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fedb5d6322cf251ec511ee1cc4d2c8ea952e7f5723d395af7dc104e23cf127f2 0.600000000000 1600349 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": 1118980, "vin": [ { "gen": { "height": 1118970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fedb5d6322cf251ec511ee1cc4d2c8ea952e7f5723d395af7dc104e23cf127f2" } } ], "extra": [ 1, 144, 60, 196, 94, 204, 33, 220, 143, 169, 240, 6, 244, 29, 9, 33, 83, 221, 202, 94, 30, 191, 9, 104, 149, 32, 101, 90, 49, 221, 11, 61, 198, 2, 17, 0, 0, 0, 7, 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