Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bdd499e3b035bc8dafef7c9692c64a84186d54cc7e4281ddf9d7ef3b816c52d

Tx prefix hash: 9af59fd3c444de854573c8ad11a7559cbbc99163dbe5852282cbec85864e63bb
Tx public key: 9168f92c64d0c852b056cedad9a9d8263d8509e3f986d45f70e9b0f18dbc036c
Timestamp: 1736999685 Timestamp [UCT]: 2025-01-16 03:54:45 Age [y:d:h:m:s]: 00:305:18:14:33
Block: 1198343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216033 RingCT/type: yes/0
Extra: 019168f92c64d0c852b056cedad9a9d8263d8509e3f986d45f70e9b0f18dbc036c02110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2bc4496351d170e39a52c66fc519c7dc92484e8108b571492b7efaf2713e20 0.600000000000 1684966 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": 1198353, "vin": [ { "gen": { "height": 1198343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2bc4496351d170e39a52c66fc519c7dc92484e8108b571492b7efaf2713e20" } } ], "extra": [ 1, 145, 104, 249, 44, 100, 208, 200, 82, 176, 86, 206, 218, 217, 169, 216, 38, 61, 133, 9, 227, 249, 134, 212, 95, 112, 233, 176, 241, 141, 188, 3, 108, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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