Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcd7988b60c139b8cb0d5d78a740aa580aea50579638b6b93f2009956724311

Tx prefix hash: ae25d5602967251aa815d4bdb9e39114a896e3f2b3442fd6a7a550942b987fae
Tx public key: 796260b1aacb3a2f394d946276082f213c1d793c8016ead739f5dcf202c623b5
Timestamp: 1722858654 Timestamp [UCT]: 2024-08-05 11:50:54 Age [y:d:h:m:s]: 00:201:04:39:59
Block: 1081253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143645 RingCT/type: yes/0
Extra: 01796260b1aacb3a2f394d946276082f213c1d793c8016ead739f5dcf202c623b5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cacfd9ec37453fddded8ced834f656cbd685f418efe56adaea5c6327d20c41f3 0.600000000000 1554928 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": 1081263, "vin": [ { "gen": { "height": 1081253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cacfd9ec37453fddded8ced834f656cbd685f418efe56adaea5c6327d20c41f3" } } ], "extra": [ 1, 121, 98, 96, 177, 170, 203, 58, 47, 57, 77, 148, 98, 118, 8, 47, 33, 60, 29, 121, 60, 128, 22, 234, 215, 57, 245, 220, 242, 2, 198, 35, 181, 2, 17, 0, 0, 0, 5, 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