Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ed6c614cd771fdbc2543bdb86ba1c95889c44d8a6dda186d71ed9170a8abab5

Tx prefix hash: f40568e97f0e6f7099b8801ad600b66f191cbed8e51a36f51eeefc829b13c036
Tx public key: 74fa427b10a63ed94982b7d1815d85984f1450ab7380f94a55a8501f7e286914
Timestamp: 1722753713 Timestamp [UCT]: 2024-08-04 06:41:53 Age [y:d:h:m:s]: 00:245:15:04:16
Block: 1080382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175435 RingCT/type: yes/0
Extra: 0174fa427b10a63ed94982b7d1815d85984f1450ab7380f94a55a8501f7e28691402110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88ee790e9dc9a617b1d2d2c7b2767e60c4d0b87f25b324c515fa2a7218a761e2 0.600000000000 1553713 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": 1080392, "vin": [ { "gen": { "height": 1080382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88ee790e9dc9a617b1d2d2c7b2767e60c4d0b87f25b324c515fa2a7218a761e2" } } ], "extra": [ 1, 116, 250, 66, 123, 16, 166, 62, 217, 73, 130, 183, 209, 129, 93, 133, 152, 79, 20, 80, 171, 115, 128, 249, 74, 85, 168, 80, 31, 126, 40, 105, 20, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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