Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb947ac3dc07d1b87669a329cb55e56fc951b724314656f76c43d4eead423982

Tx prefix hash: f7b36c1747d4cb2d278d7e2a594075a7b204cf12363b6a1074e0eb6794f0abd6
Tx public key: 394ee30b0aeef58d39408b8a9ead09e591b27d537c70c2b48e596a9927e529d5
Timestamp: 1724812519 Timestamp [UCT]: 2024-08-28 02:35:19 Age [y:d:h:m:s]: 00:293:22:41:51
Block: 1097444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209875 RingCT/type: yes/0
Extra: 01394ee30b0aeef58d39408b8a9ead09e591b27d537c70c2b48e596a9927e529d502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b36e7200bc37b9574f4a6eaa6d8c39dee429225cbd8fb33821c9859de1ad9c0 0.600000000000 1572841 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": 1097454, "vin": [ { "gen": { "height": 1097444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b36e7200bc37b9574f4a6eaa6d8c39dee429225cbd8fb33821c9859de1ad9c0" } } ], "extra": [ 1, 57, 78, 227, 11, 10, 238, 245, 141, 57, 64, 139, 138, 158, 173, 9, 229, 145, 178, 125, 83, 124, 112, 194, 180, 142, 89, 106, 153, 39, 229, 41, 213, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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