Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8f44c0dcdfae89567141be3b0ed6c459a7b10c837c73a6c11a1f35f6da9983

Tx prefix hash: aa4d7b0665fbc7df20a63d20f0e90f9453fb4faf63b9070e0a7c69c0fcdc5f30
Tx public key: 559eb6c83503840ad32217cd5e42b2e2109ca151b0f01cea96529e3b01893343
Timestamp: 1715975073 Timestamp [UCT]: 2024-05-17 19:44:33 Age [y:d:h:m:s]: 00:283:04:00:43
Block: 1024190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202359 RingCT/type: yes/0
Extra: 01559eb6c83503840ad32217cd5e42b2e2109ca151b0f01cea96529e3b01893343021100000004c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 569df7234f2ace71f6903f6f843f8224dc1dec579de513493f6fa2a21e4f32a2 0.600000000000 1489741 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": 1024200, "vin": [ { "gen": { "height": 1024190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "569df7234f2ace71f6903f6f843f8224dc1dec579de513493f6fa2a21e4f32a2" } } ], "extra": [ 1, 85, 158, 182, 200, 53, 3, 132, 10, 211, 34, 23, 205, 94, 66, 178, 226, 16, 156, 161, 81, 176, 240, 28, 234, 150, 82, 158, 59, 1, 137, 51, 67, 2, 17, 0, 0, 0, 4, 197, 69, 41, 96, 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