Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b31be910ed2ee90525ed4a85d45f5771b813e9fc058fb80284291fb6ed1bfac

Tx prefix hash: 8ed1a4457e141364bae054693a8b77a3b6b83c05b137933cd589a0b734c1ecea
Tx public key: 86a7968c0cd9afc667a9198bfa82f247deed91283c3c4e1de3a513b4dcc0fd94
Timestamp: 1577229929 Timestamp [UCT]: 2019-12-24 23:25:29 Age [y:d:h:m:s]: 05:080:23:57:10
Block: 31070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207660 RingCT/type: yes/0
Extra: 0186a7968c0cd9afc667a9198bfa82f247deed91283c3c4e1de3a513b4dcc0fd940211000000024ac5aa02000000000000000000

1 output(s) for total of 484.231517172000 dcy

stealth address amount amount idx
00: b00268b9b827f52ed6ba1f4e530bc42b57ce66974b4c39d418766ad1db5e434e 484.231517172000 51346 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": 31080, "vin": [ { "gen": { "height": 31070 } } ], "vout": [ { "amount": 484231517172, "target": { "key": "b00268b9b827f52ed6ba1f4e530bc42b57ce66974b4c39d418766ad1db5e434e" } } ], "extra": [ 1, 134, 167, 150, 140, 12, 217, 175, 198, 103, 169, 25, 139, 250, 130, 242, 71, 222, 237, 145, 40, 60, 60, 78, 29, 227, 165, 19, 180, 220, 192, 253, 148, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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