Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc514f17f8578a7547090f4851a0d395b252621a2aa43080704df88e24c9d785

Tx prefix hash: 8ff44b64d9b0108a085c990fe20c5f8bd8f22b554bb03c742a30cb39aa813cd6
Tx public key: f81102d1b0880dfa87ac74a672ee386b0e29949beb66eccb5c194d42703990f8
Timestamp: 1723536486 Timestamp [UCT]: 2024-08-13 08:08:06 Age [y:d:h:m:s]: 00:216:04:14:37
Block: 1086878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154388 RingCT/type: yes/0
Extra: 01f81102d1b0880dfa87ac74a672ee386b0e29949beb66eccb5c194d42703990f8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c271c211e7786d2b0be9a90993e9c481ac82199b05c1adcb8dbb203938cdb575 0.600000000000 1561477 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": 1086888, "vin": [ { "gen": { "height": 1086878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c271c211e7786d2b0be9a90993e9c481ac82199b05c1adcb8dbb203938cdb575" } } ], "extra": [ 1, 248, 17, 2, 209, 176, 136, 13, 250, 135, 172, 116, 166, 114, 238, 56, 107, 14, 41, 148, 155, 235, 102, 236, 203, 92, 25, 77, 66, 112, 57, 144, 248, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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