Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a228d3f6d39c950d3b6821d0990293cbb524b52a2d7a0acb464a2b5d271678

Tx prefix hash: 405eaf53c734448c7f743e5fe578de45ee527472e5a53760491a8fa10eb1d758
Tx public key: c8fba7fa38f925839ecfe9be1b5e9f01f13403bd71333ce010a2d645cc9bac03
Timestamp: 1720726979 Timestamp [UCT]: 2024-07-11 19:42:59 Age [y:d:h:m:s]: 00:246:19:12:24
Block: 1063588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176328 RingCT/type: yes/0
Extra: 01c8fba7fa38f925839ecfe9be1b5e9f01f13403bd71333ce010a2d645cc9bac0302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293f5b310d5b43c2e5f77f8d04ac5f109fc48741c2518f12f57fb1eb6af3fb4d 0.600000000000 1534105 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": 1063598, "vin": [ { "gen": { "height": 1063588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293f5b310d5b43c2e5f77f8d04ac5f109fc48741c2518f12f57fb1eb6af3fb4d" } } ], "extra": [ 1, 200, 251, 167, 250, 56, 249, 37, 131, 158, 207, 233, 190, 27, 94, 159, 1, 241, 52, 3, 189, 113, 51, 60, 224, 16, 162, 214, 69, 204, 155, 172, 3, 2, 17, 0, 0, 0, 4, 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