Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 482741fdb5d2bd3f4db1673f292d93668bf162af0abd1117d5d981ff3b27a810

Tx prefix hash: eac243557331c7cd47e456af78e7f657adab0077ae43e987991b1d5f0e3be16b
Tx public key: e540c290bf9f5221ff842e8368f8d298a4b28f6d951006b4758cd37d369f9f1d
Timestamp: 1715417991 Timestamp [UCT]: 2024-05-11 08:59:51 Age [y:d:h:m:s]: 00:244:15:04:09
Block: 1019602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175045 RingCT/type: yes/0
Extra: 01e540c290bf9f5221ff842e8368f8d298a4b28f6d951006b4758cd37d369f9f1d02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73ede4967ca2a2dc736ab7ccd82399d2dbf0ede9d2fc1063813d4f38424cc680 0.600000000000 1483617 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": 1019612, "vin": [ { "gen": { "height": 1019602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73ede4967ca2a2dc736ab7ccd82399d2dbf0ede9d2fc1063813d4f38424cc680" } } ], "extra": [ 1, 229, 64, 194, 144, 191, 159, 82, 33, 255, 132, 46, 131, 104, 248, 210, 152, 164, 178, 143, 109, 149, 16, 6, 180, 117, 140, 211, 125, 54, 159, 159, 29, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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