Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5e7001be16f661461dac9e9511f82cb8541aa5b70f8a4c64aa097e5c3f1624e

Tx prefix hash: 82de1804249c6a977a3fb33342e485adb2c98000015d9f1aac0e1e8ae4ab7595
Tx public key: 39408f7116be0b8ba6e06201717a773106e943a292202e125999f32404f11f15
Timestamp: 1733708679 Timestamp [UCT]: 2024-12-09 01:44:39 Age [y:d:h:m:s]: 00:190:17:38:20
Block: 1171115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136035 RingCT/type: yes/0
Extra: 0139408f7116be0b8ba6e06201717a773106e943a292202e125999f32404f11f15021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b54a8f668dcfbb6aec6a01e159f7b86ae1ac0439c5472b13a1470bb89fa7a8b 0.600000000000 1656852 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": 1171125, "vin": [ { "gen": { "height": 1171115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b54a8f668dcfbb6aec6a01e159f7b86ae1ac0439c5472b13a1470bb89fa7a8b" } } ], "extra": [ 1, 57, 64, 143, 113, 22, 190, 11, 139, 166, 224, 98, 1, 113, 122, 119, 49, 6, 233, 67, 162, 146, 32, 46, 18, 89, 153, 243, 36, 4, 241, 31, 21, 2, 17, 0, 0, 0, 1, 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