Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca3bc7c5ed941c295e30f0e6a1fc6d1917278c51f8a5e5be67c7fc34f072482

Tx prefix hash: 4f4873031c4c653eea8da4d1ce8aaa25221750a47e568060eeb1a27f3f414bfb
Tx public key: 185ac45da975c398b11f0a29b33d922f6366a8c51682d4ba2cfc6d2c58739772
Timestamp: 1639027849 Timestamp [UCT]: 2021-12-09 05:30:49 Age [y:d:h:m:s]: 03:149:05:32:07
Block: 391572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 885394 RingCT/type: yes/0
Extra: 01185ac45da975c398b11f0a29b33d922f6366a8c51682d4ba2cfc6d2c587397720211000000031cab2639000000000000000000

1 output(s) for total of 30.943351988000 dcy

stealth address amount amount idx
00: cc8bf0f5ae9d93c02861bae2fc0d7b1c37aab3025e6d456c912f3dd0d41211d2 30.943351988000 788003 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": 391582, "vin": [ { "gen": { "height": 391572 } } ], "vout": [ { "amount": 30943351988, "target": { "key": "cc8bf0f5ae9d93c02861bae2fc0d7b1c37aab3025e6d456c912f3dd0d41211d2" } } ], "extra": [ 1, 24, 90, 196, 93, 169, 117, 195, 152, 177, 31, 10, 41, 179, 61, 146, 47, 99, 102, 168, 197, 22, 130, 212, 186, 44, 252, 109, 44, 88, 115, 151, 114, 2, 17, 0, 0, 0, 3, 28, 171, 38, 57, 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