Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f67f59ee0b25a53fbd52214d5ad5a744761857a656ea70220f2cfea3d057d6d

Tx prefix hash: f7b4e4747de915ab164d18becc1fa5b95f3ffff97ff873e041c4bce923420a31
Tx public key: 05e183f85c8ae88034b00bcf62e9708b935b7ecd013d2cfe54c2c92e2a08629e
Timestamp: 1704288843 Timestamp [UCT]: 2024-01-03 13:34:03 Age [y:d:h:m:s]: 01:096:21:14:24
Block: 927315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330341 RingCT/type: yes/0
Extra: 0105e183f85c8ae88034b00bcf62e9708b935b7ecd013d2cfe54c2c92e2a08629e021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d87f51798644110720ac12fed1895ca6bce541c66b9daa27f5a444b047ac5f2c 0.600000000000 1385151 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": 927325, "vin": [ { "gen": { "height": 927315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d87f51798644110720ac12fed1895ca6bce541c66b9daa27f5a444b047ac5f2c" } } ], "extra": [ 1, 5, 225, 131, 248, 92, 138, 232, 128, 52, 176, 11, 207, 98, 233, 112, 139, 147, 91, 126, 205, 1, 61, 44, 254, 84, 194, 201, 46, 42, 8, 98, 158, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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