Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c2ac12209c4e87de73743ffd6ee2e2f304e783e827f61b13745fa05adcb1f47

Tx prefix hash: 3cf7f7ef57221ecf4c6665be1b4064bf364e6bae81953049f26aa1584893f9e0
Tx public key: 5197300aac8c900e23ad8d143c0c6ef01c6ff07bf560cfcf2d912ac1b4480fa3
Timestamp: 1717353871 Timestamp [UCT]: 2024-06-02 18:44:31 Age [y:d:h:m:s]: 00:346:14:38:34
Block: 1035628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247731 RingCT/type: yes/0
Extra: 015197300aac8c900e23ad8d143c0c6ef01c6ff07bf560cfcf2d912ac1b4480fa302110000000641ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 312b162565af82ca0637f5ae20aea8f3648d3cb27f5b81212e1690eac7b34fd6 0.600000000000 1504149 of 15

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": 1035638, "vin": [ { "gen": { "height": 1035628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "312b162565af82ca0637f5ae20aea8f3648d3cb27f5b81212e1690eac7b34fd6" } } ], "extra": [ 1, 81, 151, 48, 10, 172, 140, 144, 14, 35, 173, 141, 20, 60, 12, 110, 240, 28, 111, 240, 123, 245, 96, 207, 207, 45, 145, 42, 193, 180, 72, 15, 163, 2, 17, 0, 0, 0, 6, 65, 238, 28, 155, 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