Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011a27dbb23666338bf6f1d10b122a5c23a60ee9b2ff73cead98dbd2360a7cb0

Tx prefix hash: 3ced61144ee622cb79314fc0f6059a3d865db583b9bd7fd6cfc12dc6d3eeb2e5
Tx public key: 59439637fb04c96c94f39aa9fb41504b59e671b7245444e60d958a124745c5bb
Timestamp: 1705025658 Timestamp [UCT]: 2024-01-12 02:14:18 Age [y:d:h:m:s]: 01:122:03:25:17
Block: 933394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348422 RingCT/type: yes/0
Extra: 0159439637fb04c96c94f39aa9fb41504b59e671b7245444e60d958a124745c5bb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f2cacb021da943f785dbe481b171a97e52c915b48999cc84543d88f2cc58faa 0.600000000000 1391356 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": 933404, "vin": [ { "gen": { "height": 933394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f2cacb021da943f785dbe481b171a97e52c915b48999cc84543d88f2cc58faa" } } ], "extra": [ 1, 89, 67, 150, 55, 251, 4, 201, 108, 148, 243, 154, 169, 251, 65, 80, 75, 89, 230, 113, 183, 36, 84, 68, 230, 13, 149, 138, 18, 71, 69, 197, 187, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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