Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5541f2f97bb40fb3360acf3eb6e3f23e37a1ace2f50a28ad5d8866cc0f6326a

Tx prefix hash: 29c9bf8f4316a68b7315a0acbcd47157a548c90530d2f716da94da37aa2f1c7e
Tx public key: d0d51d6b1e0de8e06d80835f37ff9912cfe7361678ab4651c979c6046798714c
Timestamp: 1720085919 Timestamp [UCT]: 2024-07-04 09:38:39 Age [y:d:h:m:s]: 00:270:10:46:47
Block: 1058268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193231 RingCT/type: yes/0
Extra: 01d0d51d6b1e0de8e06d80835f37ff9912cfe7361678ab4651c979c6046798714c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0103e0e3ed884e50fd9a1d6d5f1c1b668a459708119ba119a19c9cbea6e4401f 0.600000000000 1528717 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": 1058278, "vin": [ { "gen": { "height": 1058268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0103e0e3ed884e50fd9a1d6d5f1c1b668a459708119ba119a19c9cbea6e4401f" } } ], "extra": [ 1, 208, 213, 29, 107, 30, 13, 232, 224, 109, 128, 131, 95, 55, 255, 153, 18, 207, 231, 54, 22, 120, 171, 70, 81, 201, 121, 198, 4, 103, 152, 113, 76, 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