Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11551a8a99217f9302ccb97c4f5bb95d4ce8308379203cd8accd1400262c77a9

Tx prefix hash: bbff32383f782abf60c7742cc9af01640c5b3b4f21cbc31c1836357e08b32dfd
Tx public key: 42b99a52fe55f8923e1d334bf8038a34f9ae0ef3b4d732d329287786273ac63f
Timestamp: 1704416860 Timestamp [UCT]: 2024-01-05 01:07:40 Age [y:d:h:m:s]: 01:102:05:14:19
Block: 928341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334185 RingCT/type: yes/0
Extra: 0142b99a52fe55f8923e1d334bf8038a34f9ae0ef3b4d732d329287786273ac63f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f3f214ac8080a04dd3703684d84f972af69a6ca932b173a804c1171fd1e3a5 0.600000000000 1386199 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": 928351, "vin": [ { "gen": { "height": 928341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f3f214ac8080a04dd3703684d84f972af69a6ca932b173a804c1171fd1e3a5" } } ], "extra": [ 1, 66, 185, 154, 82, 254, 85, 248, 146, 62, 29, 51, 75, 248, 3, 138, 52, 249, 174, 14, 243, 180, 215, 50, 211, 41, 40, 119, 134, 39, 58, 198, 63, 2, 17, 0, 0, 0, 1, 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