Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443db94fee3b1a4699258ac28acfaeff56bc1e90d1795ac715040b5d7a0ab398

Tx prefix hash: 03c94de478b40a9dbfcfb3ee93fb98dcd81083ff49c786545c52d99956f8cd5a
Tx public key: 4b1bf86bc823d4b15a5b1ed15f28c805d5dbc716ea4b811cd2aae9d7c48995f2
Timestamp: 1732290930 Timestamp [UCT]: 2024-11-22 15:55:30 Age [y:d:h:m:s]: 00:001:10:33:55
Block: 1159358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1037 RingCT/type: yes/0
Extra: 014b1bf86bc823d4b15a5b1ed15f28c805d5dbc716ea4b811cd2aae9d7c48995f2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecc71d749c0bd61ca2a7955285ae501c3d14665900de97b30d31c4978823face 0.600000000000 1644991 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": 1159368, "vin": [ { "gen": { "height": 1159358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecc71d749c0bd61ca2a7955285ae501c3d14665900de97b30d31c4978823face" } } ], "extra": [ 1, 75, 27, 248, 107, 200, 35, 212, 177, 90, 91, 30, 209, 95, 40, 200, 5, 213, 219, 199, 22, 234, 75, 129, 28, 210, 170, 233, 215, 196, 137, 149, 242, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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