Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04cbaa36abc63445a0ae73c6e09fc7682c4c28c4f8cdf23ae508ae5ce4aeec63

Tx prefix hash: bccbba708b97ea37b2ea61305edb10fa4469b46d241069541a812d17a09951eb
Tx public key: fa4d4a6fff3d02bf0dfcce83a15be50ce73a809edfc8fc78dbaa9bb9e853665f
Timestamp: 1719724008 Timestamp [UCT]: 2024-06-30 05:06:48 Age [y:d:h:m:s]: 00:291:01:19:55
Block: 1055260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207980 RingCT/type: yes/0
Extra: 01fa4d4a6fff3d02bf0dfcce83a15be50ce73a809edfc8fc78dbaa9bb9e853665f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ea4f858c969f9a56489f30392edf68c95619822a8b01e4a84de92cd822bd025 0.600000000000 1525657 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": 1055270, "vin": [ { "gen": { "height": 1055260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ea4f858c969f9a56489f30392edf68c95619822a8b01e4a84de92cd822bd025" } } ], "extra": [ 1, 250, 77, 74, 111, 255, 61, 2, 191, 13, 252, 206, 131, 161, 91, 229, 12, 231, 58, 128, 158, 223, 200, 252, 120, 219, 170, 155, 185, 232, 83, 102, 95, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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