Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f977861b26dd129863dcbd17990f2fbac3bb2b49140d0c037e31d30407947f70

Tx prefix hash: 190afe9fbdba423452578d6c94f46cff193b09bf3df45ba2dc20e6aa4f141661
Tx public key: 47e35575533a9bc6f1c1c9cce0635032669bdc8a339fc12bfb98e7ea2715f40d
Timestamp: 1713376564 Timestamp [UCT]: 2024-04-17 17:56:04 Age [y:d:h:m:s]: 01:022:08:00:33
Block: 1002637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276927 RingCT/type: yes/0
Extra: 0147e35575533a9bc6f1c1c9cce0635032669bdc8a339fc12bfb98e7ea2715f40d02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3a1c3c93cb8c3b2abfdf887dcd02f150ce874a7d7fcb2ef982728101e331b9a 0.600000000000 1463155 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": 1002647, "vin": [ { "gen": { "height": 1002637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3a1c3c93cb8c3b2abfdf887dcd02f150ce874a7d7fcb2ef982728101e331b9a" } } ], "extra": [ 1, 71, 227, 85, 117, 83, 58, 155, 198, 241, 193, 201, 204, 224, 99, 80, 50, 102, 155, 220, 138, 51, 159, 193, 43, 251, 152, 231, 234, 39, 21, 244, 13, 2, 17, 0, 0, 0, 7, 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