Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a515730e897f9c14cc1f5a1f589d9227ddd27c0638256be6204ffc4e15eda3e4

Tx prefix hash: e1fc30c618cc46639af00dedc848ba80b899ba7b2e4475a86f2c060fd5564beb
Tx public key: a0e1f341f81b5b8cb85e59390f4f9e5d150569dd173f90ac4461ee16ffa1db9f
Timestamp: 1738388268 Timestamp [UCT]: 2025-02-01 05:37:48 Age [y:d:h:m:s]: 00:293:06:47:17
Block: 1209581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207360 RingCT/type: yes/0
Extra: 01a0e1f341f81b5b8cb85e59390f4f9e5d150569dd173f90ac4461ee16ffa1db9f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e12bee43c4ef51831a270d9c2bcff8b94a4d4e7f527879f1483f2ce1a10719c 0.600000000000 1696326 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": 1209591, "vin": [ { "gen": { "height": 1209581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e12bee43c4ef51831a270d9c2bcff8b94a4d4e7f527879f1483f2ce1a10719c" } } ], "extra": [ 1, 160, 225, 243, 65, 248, 27, 91, 140, 184, 94, 89, 57, 15, 79, 158, 93, 21, 5, 105, 221, 23, 63, 144, 172, 68, 97, 238, 22, 255, 161, 219, 159, 2, 17, 0, 0, 0, 2, 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