Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efdfb1fc91660e170505d18a92098d38b770f7b74cabffe063b3e56f8803858f

Tx prefix hash: 2ab28bae0901bc4d2177f5df58604025ad74c0f31ef7c78d4de1662004555136
Tx public key: 5f1525e83b202a0d44ee6fa20ce46fca4aea4d03ffcae519e43fdcb99b67560e
Timestamp: 1710410812 Timestamp [UCT]: 2024-03-14 10:06:52 Age [y:d:h:m:s]: 01:018:10:33:28
Block: 978076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274135 RingCT/type: yes/0
Extra: 015f1525e83b202a0d44ee6fa20ce46fca4aea4d03ffcae519e43fdcb99b67560e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dbae1b37a0009ea30d3f033404d5f16064bb24e91419f53a03d14b1115a3a41 0.600000000000 1438093 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": 978086, "vin": [ { "gen": { "height": 978076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dbae1b37a0009ea30d3f033404d5f16064bb24e91419f53a03d14b1115a3a41" } } ], "extra": [ 1, 95, 21, 37, 232, 59, 32, 42, 13, 68, 238, 111, 162, 12, 228, 111, 202, 74, 234, 77, 3, 255, 202, 229, 25, 228, 63, 220, 185, 155, 103, 86, 14, 2, 17, 0, 0, 0, 3, 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