Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b44c5521af385f08596993c6d3f27c73b669eb95b68bac71c9bb7d8864b11f79

Tx prefix hash: 63e3964942045d130f3a851069bfb9959c29841d116da0d889042317ad3cf819
Tx public key: 2c22e8c8f5a06d8040b31d244231f06a7407db7272b19c77d34f3a663e0f2f67
Timestamp: 1719591799 Timestamp [UCT]: 2024-06-28 16:23:19 Age [y:d:h:m:s]: 00:288:23:47:34
Block: 1054166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206516 RingCT/type: yes/0
Extra: 012c22e8c8f5a06d8040b31d244231f06a7407db7272b19c77d34f3a663e0f2f6702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 777d549eebbf61e714f5baacb00c0942b22570c8ea6fd945010c5d572dea3977 0.600000000000 1524525 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": 1054176, "vin": [ { "gen": { "height": 1054166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "777d549eebbf61e714f5baacb00c0942b22570c8ea6fd945010c5d572dea3977" } } ], "extra": [ 1, 44, 34, 232, 200, 245, 160, 109, 128, 64, 179, 29, 36, 66, 49, 240, 106, 116, 7, 219, 114, 114, 177, 156, 119, 211, 79, 58, 102, 62, 15, 47, 103, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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