Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dddb5576591a94acb17b99cd35606d7dcd4636dc37c3aaee503aa64e956f3f0

Tx prefix hash: 4aa890348b86454c71d61dc6e88770980304350a403daf9d21ed2f893aabcb8b
Tx public key: d59ad4174e74d603aed0c549d4ff853dc31f9f667b05c5b0da8f7af05390cd30
Timestamp: 1728020994 Timestamp [UCT]: 2024-10-04 05:49:54 Age [y:d:h:m:s]: 00:110:19:25:48
Block: 1124059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79170 RingCT/type: yes/0
Extra: 01d59ad4174e74d603aed0c549d4ff853dc31f9f667b05c5b0da8f7af05390cd3002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74d96e2252aa4fbe5de4432f000ae8e1979eaef4550129b110974129a66cfbe7 0.600000000000 1606622 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": 1124069, "vin": [ { "gen": { "height": 1124059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74d96e2252aa4fbe5de4432f000ae8e1979eaef4550129b110974129a66cfbe7" } } ], "extra": [ 1, 213, 154, 212, 23, 78, 116, 214, 3, 174, 208, 197, 73, 212, 255, 133, 61, 195, 31, 159, 102, 123, 5, 197, 176, 218, 143, 122, 240, 83, 144, 205, 48, 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