Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc7640a3b196befd130d1e8571c1f42581339aff639dcde7f08ab17d7ef026f

Tx prefix hash: 8380f901987cce33a81e12ce20a456e47450a17c06ea60a65fec95dc9ea27979
Tx public key: bbb1a17b308793f5cc53a80eb66e95ae0d796589e49def2fca6d31434064f64d
Timestamp: 1580378237 Timestamp [UCT]: 2020-01-30 09:57:17 Age [y:d:h:m:s]: 04:333:07:30:43
Block: 55329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129112 RingCT/type: yes/0
Extra: 01bbb1a17b308793f5cc53a80eb66e95ae0d796589e49def2fca6d31434064f64d021100000002b221b3d1000000000000000000

1 output(s) for total of 402.413813366000 dcy

stealth address amount amount idx
00: 0572373811763f34964468bd2f865a39f24d97671c6938a444b445cdd57ffbb8 402.413813366000 102151 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": 55339, "vin": [ { "gen": { "height": 55329 } } ], "vout": [ { "amount": 402413813366, "target": { "key": "0572373811763f34964468bd2f865a39f24d97671c6938a444b445cdd57ffbb8" } } ], "extra": [ 1, 187, 177, 161, 123, 48, 135, 147, 245, 204, 83, 168, 14, 182, 110, 149, 174, 13, 121, 101, 137, 228, 157, 239, 47, 202, 109, 49, 67, 64, 100, 246, 77, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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