Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab31b4428042bf438bdc2ced62a42b9a0f07bfa974519f4af612a4077aeb62a

Tx prefix hash: 4bdd566a7f8f34806cae390023d9ede6df46c7c579ea9e5ceab430ed051d60d3
Tx public key: 4def667e53d833d93aa937015e8ddc2fd19aa2c99e0ef5a562f0662a3e984b41
Timestamp: 1711514412 Timestamp [UCT]: 2024-03-27 04:40:12 Age [y:d:h:m:s]: 01:015:03:56:22
Block: 987228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271791 RingCT/type: yes/0
Extra: 014def667e53d833d93aa937015e8ddc2fd19aa2c99e0ef5a562f0662a3e984b4102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bcd17a611a88ad1154f7eae520386a6ee4b21953bd6ebf956d9644a38e474aa 0.600000000000 1447469 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": 987238, "vin": [ { "gen": { "height": 987228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bcd17a611a88ad1154f7eae520386a6ee4b21953bd6ebf956d9644a38e474aa" } } ], "extra": [ 1, 77, 239, 102, 126, 83, 216, 51, 217, 58, 169, 55, 1, 94, 141, 220, 47, 209, 154, 162, 201, 158, 14, 245, 165, 98, 240, 102, 42, 62, 152, 75, 65, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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