Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91203a78503413f4c3921d76f3baa0aa3cb751f69eefe68becc293b117fc721

Tx prefix hash: 626f1b225d8d8d5a1ad378ec226b2a06a9a06748a5f8d71b68ab84cf705cd028
Tx public key: e9f19e7b5d3b30b06d9953c91cd492e83676fc0eb7270934dec005aba508f0d2
Timestamp: 1721107839 Timestamp [UCT]: 2024-07-16 05:30:39 Age [y:d:h:m:s]: 00:335:05:52:06
Block: 1066756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239451 RingCT/type: yes/0
Extra: 01e9f19e7b5d3b30b06d9953c91cd492e83676fc0eb7270934dec005aba508f0d202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527ddb0d7e7aa89cff76dd1dc66cd2df2438566dd6a67976616e1641f8000293 0.600000000000 1537423 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": 1066766, "vin": [ { "gen": { "height": 1066756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527ddb0d7e7aa89cff76dd1dc66cd2df2438566dd6a67976616e1641f8000293" } } ], "extra": [ 1, 233, 241, 158, 123, 93, 59, 48, 176, 109, 153, 83, 201, 28, 212, 146, 232, 54, 118, 252, 14, 183, 39, 9, 52, 222, 192, 5, 171, 165, 8, 240, 210, 2, 17, 0, 0, 0, 5, 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