Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d92ee87b57cba3cbf18f6f2aab99223b8c0ec3727dc780bf807c87c090967b

Tx prefix hash: d2f633818359d3767f19ab4392c0fefb7b994206570cfd9ecdb136fd9f1f9f41
Tx public key: 45b820f12da9c14225e98083a1d696766f73673a15fb5af1349e8b14d4e880c5
Timestamp: 1737111170 Timestamp [UCT]: 2025-01-17 10:52:50 Age [y:d:h:m:s]: 00:059:00:21:46
Block: 1199269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41966 RingCT/type: yes/0
Extra: 0145b820f12da9c14225e98083a1d696766f73673a15fb5af1349e8b14d4e880c5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78c2a4a9960c5c9a895825f61e2a0040cdd2d4539187e930cddf1f0fff677ab7 0.600000000000 1685898 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": 1199279, "vin": [ { "gen": { "height": 1199269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78c2a4a9960c5c9a895825f61e2a0040cdd2d4539187e930cddf1f0fff677ab7" } } ], "extra": [ 1, 69, 184, 32, 241, 45, 169, 193, 66, 37, 233, 128, 131, 161, 214, 150, 118, 111, 115, 103, 58, 21, 251, 90, 241, 52, 158, 139, 20, 212, 232, 128, 197, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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