Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0f4e48eafd1fa415b776f5960f3c8bf1413b581157b8598f5a4762e909e7f8

Tx prefix hash: 049e07bbce7c4465c8071048bef7e4bb0b5a9bd09dd065505c7ec0f653918647
Tx public key: 9ee7838a3079ae59ab129095c84cd34ff3201697b3847f7a0b44c485a30361ef
Timestamp: 1728037973 Timestamp [UCT]: 2024-10-04 10:32:53 Age [y:d:h:m:s]: 00:055:00:45:28
Block: 1124201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39312 RingCT/type: yes/0
Extra: 019ee7838a3079ae59ab129095c84cd34ff3201697b3847f7a0b44c485a30361ef02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8b29434d5ab3ffaaae8ecca692a72ba10cd9f1344b45c18a4aa8c2f9545cf9d 0.600000000000 1606792 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": 1124211, "vin": [ { "gen": { "height": 1124201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8b29434d5ab3ffaaae8ecca692a72ba10cd9f1344b45c18a4aa8c2f9545cf9d" } } ], "extra": [ 1, 158, 231, 131, 138, 48, 121, 174, 89, 171, 18, 144, 149, 200, 76, 211, 79, 243, 32, 22, 151, 179, 132, 127, 122, 11, 68, 196, 133, 163, 3, 97, 239, 2, 17, 0, 0, 0, 12, 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