Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595fb0467c67c5e9b0141b7b6f7394f88f5152bfc42ba5182c86ee8884eb69b4

Tx prefix hash: b0f1d3e8a630fcff8e8a4627c83d10d5539dc65e2aa3adb779e4040ac4909c8d
Tx public key: c09e1084df179b1e9df30701ad6cfaa50d4a3ef75e12f19cb89b5ebfbf4bf602
Timestamp: 1648274232 Timestamp [UCT]: 2022-03-26 05:57:12 Age [y:d:h:m:s]: 03:049:12:14:20
Block: 466605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 815591 RingCT/type: yes/0
Extra: 01c09e1084df179b1e9df30701ad6cfaa50d4a3ef75e12f19cb89b5ebfbf4bf60202110000000c4a0f5013000000000000000000

1 output(s) for total of 17.455978265000 dcy

stealth address amount amount idx
00: 895eb337852bdb09e2b21e8d8359b839243501002f84fe17a2f9458e77af1ab8 17.455978265000 884950 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": 466615, "vin": [ { "gen": { "height": 466605 } } ], "vout": [ { "amount": 17455978265, "target": { "key": "895eb337852bdb09e2b21e8d8359b839243501002f84fe17a2f9458e77af1ab8" } } ], "extra": [ 1, 192, 158, 16, 132, 223, 23, 155, 30, 157, 243, 7, 1, 173, 108, 250, 165, 13, 74, 62, 247, 94, 18, 241, 156, 184, 155, 94, 191, 191, 75, 246, 2, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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