Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7abc0b4070109ea0fbf4e4f265c6bf5fa1a20df74c36d1f6dc210e28312c535d

Tx prefix hash: 7190c949ad12bf16518bb951e804106de5b49d1e541d3bcde4b1eaea5c3ea142
Tx public key: 5e74e3d2382ca7c2141e36e24373688642255ae45cd86490528901de83d54281
Timestamp: 1735962133 Timestamp [UCT]: 2025-01-04 03:42:13 Age [y:d:h:m:s]: 00:163:19:04:22
Block: 1189758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116784 RingCT/type: yes/0
Extra: 015e74e3d2382ca7c2141e36e24373688642255ae45cd86490528901de83d542810211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2cd3f8b3cde791e145a971a4562c3dc0d556f1a8d597bfa33cbb3b1e88943ea 0.600000000000 1676269 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": 1189768, "vin": [ { "gen": { "height": 1189758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2cd3f8b3cde791e145a971a4562c3dc0d556f1a8d597bfa33cbb3b1e88943ea" } } ], "extra": [ 1, 94, 116, 227, 210, 56, 44, 167, 194, 20, 30, 54, 226, 67, 115, 104, 134, 66, 37, 90, 228, 92, 216, 100, 144, 82, 137, 1, 222, 131, 213, 66, 129, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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