Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b4f20556313b6cac84ea01abbdcc4ef322fa6c8c53d1f785a5d605819562cb0

Tx prefix hash: cf6131efc412d18bddae30e1827a7e7a8e295a12c55975aea33f3e22e4e238d9
Tx public key: 809f33ed95418ca05188bb1449acc0c2171891dd62661e7157eff7433e57357a
Timestamp: 1712085539 Timestamp [UCT]: 2024-04-02 19:18:59 Age [y:d:h:m:s]: 01:232:08:46:05
Block: 991910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424783 RingCT/type: yes/0
Extra: 01809f33ed95418ca05188bb1449acc0c2171891dd62661e7157eff7433e57357a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300ab087c35a1f70c5f7f08eb23f4cbc4dd325021a6dcdb903b95e5c39193937 0.600000000000 1452246 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": 991920, "vin": [ { "gen": { "height": 991910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300ab087c35a1f70c5f7f08eb23f4cbc4dd325021a6dcdb903b95e5c39193937" } } ], "extra": [ 1, 128, 159, 51, 237, 149, 65, 140, 160, 81, 136, 187, 20, 73, 172, 192, 194, 23, 24, 145, 221, 98, 102, 30, 113, 87, 239, 247, 67, 62, 87, 53, 122, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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