Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4abe69012e71e80e2de45023af43bd9a2a1cb6fc594d3bd38cf202d1c1876da4

Tx prefix hash: a66a53c2fb8ccfb5a5455d9bd412c0fa1902f984fa06854a4f30ee47049741ae
Tx public key: cdf8d3cde594f3a43a9e6f00be31cec64c052bf6b187ba39fd2a63f315355b60
Timestamp: 1621463987 Timestamp [UCT]: 2021-05-19 22:39:47 Age [y:d:h:m:s]: 03:191:13:15:35
Block: 263701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898398 RingCT/type: yes/0
Extra: 01cdf8d3cde594f3a43a9e6f00be31cec64c052bf6b187ba39fd2a63f315355b600211000000019c1fbdcc000000000000000000

1 output(s) for total of 82.082327467000 dcy

stealth address amount amount idx
00: 37f8e72c8e3ff70b503a2e87ba083b89f30a85926daf9bab9ccb5a0aef384506 82.082327467000 554605 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": 263711, "vin": [ { "gen": { "height": 263701 } } ], "vout": [ { "amount": 82082327467, "target": { "key": "37f8e72c8e3ff70b503a2e87ba083b89f30a85926daf9bab9ccb5a0aef384506" } } ], "extra": [ 1, 205, 248, 211, 205, 229, 148, 243, 164, 58, 158, 111, 0, 190, 49, 206, 198, 76, 5, 43, 246, 177, 135, 186, 57, 253, 42, 99, 243, 21, 53, 91, 96, 2, 17, 0, 0, 0, 1, 156, 31, 189, 204, 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