Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbfed59058c36a307a946c39231c3e9a3de4d7b92dd0736ecdbb5e1443050736

Tx prefix hash: a229fbd1b4cbb54e71f1fd162582934f044e31a8e41e5f7a4616387dd6aefbda
Tx public key: 4790cbdee9abd39aa5488051320c76a009af760d201518724b7d8f68ad0b091e
Timestamp: 1731165953 Timestamp [UCT]: 2024-11-09 15:25:53 Age [y:d:h:m:s]: 00:133:09:12:13
Block: 1150047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95141 RingCT/type: yes/0
Extra: 014790cbdee9abd39aa5488051320c76a009af760d201518724b7d8f68ad0b091e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7054eab07f96925899e2c439f1ee91cd4df1ef5aaacd8032a32df475ec5c4b4 0.600000000000 1635244 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": 1150057, "vin": [ { "gen": { "height": 1150047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7054eab07f96925899e2c439f1ee91cd4df1ef5aaacd8032a32df475ec5c4b4" } } ], "extra": [ 1, 71, 144, 203, 222, 233, 171, 211, 154, 165, 72, 128, 81, 50, 12, 118, 160, 9, 175, 118, 13, 32, 21, 24, 114, 75, 125, 143, 104, 173, 11, 9, 30, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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