Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 139adb07657ab0c3d149882374726d3bb6c48a819ca7ccfb9d66cdca79193427

Tx prefix hash: bfcf5d6ae2e065a66fc4525f15de01f4babb7cc11d7b703d727f9341aa623f01
Tx public key: 68bce6bb3e0e5cbe7ab0bf1e8bb731e594a0f8172c2da27e3404c93304f3f3c2
Timestamp: 1707067081 Timestamp [UCT]: 2024-02-04 17:18:01 Age [y:d:h:m:s]: 00:355:10:52:56
Block: 950323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254427 RingCT/type: yes/0
Extra: 0168bce6bb3e0e5cbe7ab0bf1e8bb731e594a0f8172c2da27e3404c93304f3f3c20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf85d04a2064f1e43aeac895749d162fee958cc5df0f37f09cc5d4c87e6502b0 0.600000000000 1408921 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": 950333, "vin": [ { "gen": { "height": 950323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf85d04a2064f1e43aeac895749d162fee958cc5df0f37f09cc5d4c87e6502b0" } } ], "extra": [ 1, 104, 188, 230, 187, 62, 14, 92, 190, 122, 176, 191, 30, 139, 183, 49, 229, 148, 160, 248, 23, 44, 45, 162, 126, 52, 4, 201, 51, 4, 243, 243, 194, 2, 17, 0, 0, 0, 1, 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