Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 908a888fe208d742c2e7e18db4e7769ae08db1c335021f14ee152a92033e88a3

Tx prefix hash: 29845b48cd8794f08004b4d923afae270131645e2688aaa54f1727b11df1539e
Tx public key: 2c62e1f34034c0bc1e46c80d39c9436aac0ec1f9304b9b1820d66c2f51839d3f
Timestamp: 1731007666 Timestamp [UCT]: 2024-11-07 19:27:46 Age [y:d:h:m:s]: 00:149:01:45:36
Block: 1148729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106368 RingCT/type: yes/0
Extra: 012c62e1f34034c0bc1e46c80d39c9436aac0ec1f9304b9b1820d66c2f51839d3f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da9523e77b2b33613101600152018b00b1d0b1fc0900e764638b518f8d0d0a26 0.600000000000 1633648 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": 1148739, "vin": [ { "gen": { "height": 1148729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da9523e77b2b33613101600152018b00b1d0b1fc0900e764638b518f8d0d0a26" } } ], "extra": [ 1, 44, 98, 225, 243, 64, 52, 192, 188, 30, 70, 200, 13, 57, 201, 67, 106, 172, 14, 193, 249, 48, 75, 155, 24, 32, 214, 108, 47, 81, 131, 157, 63, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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