Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539e17b7ae0a56874abbdf2106e3acedcb4a7c58cbb839d280f9a516a7e12252

Tx prefix hash: df17e70d19d8c0ca63b12c12c6e2488e15c7114ae99bc32459f2c81e9542e3a0
Tx public key: 70aa75e9ce6c20b57a6de9e002f229ba6c09c55cf7bfe114f0ed121b080989d6
Timestamp: 1682521711 Timestamp [UCT]: 2023-04-26 15:08:31 Age [y:d:h:m:s]: 01:302:18:01:46
Block: 747090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477585 RingCT/type: yes/0
Extra: 0170aa75e9ce6c20b57a6de9e002f229ba6c09c55cf7bfe114f0ed121b080989d6021100000001faf35c9c000000000000000000

1 output(s) for total of 2.053907617000 dcy

stealth address amount amount idx
00: 9c265faee3fd9fc2ca3bdf0078a207408b7152d48f0e9a6255393f1df92a13fa 2.053907617000 1194727 of 0

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": 747100, "vin": [ { "gen": { "height": 747090 } } ], "vout": [ { "amount": 2053907617, "target": { "key": "9c265faee3fd9fc2ca3bdf0078a207408b7152d48f0e9a6255393f1df92a13fa" } } ], "extra": [ 1, 112, 170, 117, 233, 206, 108, 32, 181, 122, 109, 233, 224, 2, 242, 41, 186, 108, 9, 197, 92, 247, 191, 225, 20, 240, 237, 18, 27, 8, 9, 137, 214, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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