Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56708ef372ef6e73a91735243810cb2306aaedf7c68a28e6b4012ee18f03889

Tx prefix hash: 9c6cdc48c6335f6d956b28e007f76a7f8fb0f2fafc5aabc400e791db091f75c6
Tx public key: 1a1949b5ebdac5013f3f1c2d66a28487f9b07fc04b7f69f0319f356f98bb25bc
Timestamp: 1707952303 Timestamp [UCT]: 2024-02-14 23:11:43 Age [y:d:h:m:s]: 01:077:06:34:59
Block: 957666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316282 RingCT/type: yes/0
Extra: 011a1949b5ebdac5013f3f1c2d66a28487f9b07fc04b7f69f0319f356f98bb25bc0211000000016d0f39ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be6fe6f36cdb842db865c0b00ba5ed72145732741e2066c2fc68fbb982549a9 0.600000000000 1416986 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": 957676, "vin": [ { "gen": { "height": 957666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be6fe6f36cdb842db865c0b00ba5ed72145732741e2066c2fc68fbb982549a9" } } ], "extra": [ 1, 26, 25, 73, 181, 235, 218, 197, 1, 63, 63, 28, 45, 102, 162, 132, 135, 249, 176, 127, 192, 75, 127, 105, 240, 49, 159, 53, 111, 152, 187, 37, 188, 2, 17, 0, 0, 0, 1, 109, 15, 57, 206, 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