Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a06752aced77fa1d41c59e431cda6eaa561d49289b2e48408117d2f341cb714

Tx prefix hash: de6bd07b55b642a5ff15d0f7f30b74acd83e1cc3181e39072624c02ed0fcec19
Tx public key: a75b7bf87dc73ffde016c846f7e962a3d2c2e1c752b3826e1cbe2ad7b0b5b9b0
Timestamp: 1710594674 Timestamp [UCT]: 2024-03-16 13:11:14 Age [y:d:h:m:s]: 01:009:13:56:16
Block: 979598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267796 RingCT/type: yes/0
Extra: 01a75b7bf87dc73ffde016c846f7e962a3d2c2e1c752b3826e1cbe2ad7b0b5b9b00211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a24120ccfbd986267a294dfdbff979d379a9c98fcd8a925b4f9230c1d43818c 0.600000000000 1439635 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": 979608, "vin": [ { "gen": { "height": 979598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a24120ccfbd986267a294dfdbff979d379a9c98fcd8a925b4f9230c1d43818c" } } ], "extra": [ 1, 167, 91, 123, 248, 125, 199, 63, 253, 224, 22, 200, 70, 247, 233, 98, 163, 210, 194, 225, 199, 82, 179, 130, 110, 28, 190, 42, 215, 176, 181, 185, 176, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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