Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea04c82b1add2576e9f22d0d48e786a1a532c797720480e009b4a792cf54918b

Tx prefix hash: ea68bd41ac4f005e4ecfc69d4d99de1b96c40fce9568dc7c532478fcf5a9a8a1
Tx public key: 6e49e4131df158b9116cc4169ab4cdfc5040cf3e9ab41010bf360d051ead2b61
Timestamp: 1734944811 Timestamp [UCT]: 2024-12-23 09:06:51 Age [y:d:h:m:s]: 00:176:12:26:10
Block: 1181367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125841 RingCT/type: yes/0
Extra: 016e49e4131df158b9116cc4169ab4cdfc5040cf3e9ab41010bf360d051ead2b61021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a6a19fc289c71cc1f9e3ea086104eb6cbc2e03490f9f3ff160adf5984f6df0c 0.600000000000 1667786 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": 1181377, "vin": [ { "gen": { "height": 1181367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a6a19fc289c71cc1f9e3ea086104eb6cbc2e03490f9f3ff160adf5984f6df0c" } } ], "extra": [ 1, 110, 73, 228, 19, 29, 241, 88, 185, 17, 108, 196, 22, 154, 180, 205, 252, 80, 64, 207, 62, 154, 180, 16, 16, 191, 54, 13, 5, 30, 173, 43, 97, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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