Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f66ecee9bfc530cab624b3af4140d8819157980db812bcbdc901f8d4ac8361

Tx prefix hash: bbd19c7c40100e377e6d836270daef84b5d32420c8f3302ccf4c93d796d4c0c8
Tx public key: 93423dcaee3a226fdee08729ff042d6e94511949ed1e128e52c7813779d1e5e9
Timestamp: 1718455010 Timestamp [UCT]: 2024-06-15 12:36:50 Age [y:d:h:m:s]: 00:272:12:18:49
Block: 1044761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194735 RingCT/type: yes/0
Extra: 0193423dcaee3a226fdee08729ff042d6e94511949ed1e128e52c7813779d1e5e90211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8b63deffe3a1e37843d6d960e6fb5c28f74297932bc6e097ea5f86830bc3911 0.600000000000 1514154 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": 1044771, "vin": [ { "gen": { "height": 1044761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8b63deffe3a1e37843d6d960e6fb5c28f74297932bc6e097ea5f86830bc3911" } } ], "extra": [ 1, 147, 66, 61, 202, 238, 58, 34, 111, 222, 224, 135, 41, 255, 4, 45, 110, 148, 81, 25, 73, 237, 30, 18, 142, 82, 199, 129, 55, 121, 209, 229, 233, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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