Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ef5cf0b530eec8b82e8d0b6cac31c7b49ed9bbb45f393f62cbb1f25e85dbec

Tx prefix hash: f35aa099f5fca02645b7ce1d338c460ea9b20f482dac2ccb7f4bc4aa0b010593
Tx public key: b92eefd39fd399fd7348e603137ab102309da876f36ecfbadd6a816af1a154fd
Timestamp: 1726457557 Timestamp [UCT]: 2024-09-16 03:32:37 Age [y:d:h:m:s]: 00:218:09:51:06
Block: 1111089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155937 RingCT/type: yes/0
Extra: 01b92eefd39fd399fd7348e603137ab102309da876f36ecfbadd6a816af1a154fd021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bd803b16f8d60dc17c61ced51f2b7be6624d5ceed3eb3cf90b02c42c45b5b7e 0.600000000000 1589928 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": 1111099, "vin": [ { "gen": { "height": 1111089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bd803b16f8d60dc17c61ced51f2b7be6624d5ceed3eb3cf90b02c42c45b5b7e" } } ], "extra": [ 1, 185, 46, 239, 211, 159, 211, 153, 253, 115, 72, 230, 3, 19, 122, 177, 2, 48, 157, 168, 118, 243, 110, 207, 186, 221, 106, 129, 106, 241, 161, 84, 253, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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