Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a854be7baafb252b94705404109ef534bb272405a75f207a9da630706c456e

Tx prefix hash: f6ce62aa7929824f8dcd7d5e9dfac5403b7229b4a2f8d0d371536faa6c139821
Tx public key: 8055d2daf32c230a2fad79b9777796d1e0f8d22a5d3a59c4af1b694f760e35fd
Timestamp: 1665507695 Timestamp [UCT]: 2022-10-11 17:01:35 Age [y:d:h:m:s]: 02:039:11:51:39
Block: 606909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549976 RingCT/type: yes/0
Extra: 018055d2daf32c230a2fad79b9777796d1e0f8d22a5d3a59c4af1b694f760e35fd021100000003e6d27f9c000000000000000000

1 output(s) for total of 5.984923351000 dcy

stealth address amount amount idx
00: 9fb7a2f866d1bd353c901673ba8cee17e4b520bc96454c9fe21e2be4e7ff75b7 5.984923351000 1043411 of 0

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": 606919, "vin": [ { "gen": { "height": 606909 } } ], "vout": [ { "amount": 5984923351, "target": { "key": "9fb7a2f866d1bd353c901673ba8cee17e4b520bc96454c9fe21e2be4e7ff75b7" } } ], "extra": [ 1, 128, 85, 210, 218, 243, 44, 35, 10, 47, 173, 121, 185, 119, 119, 150, 209, 224, 248, 210, 42, 93, 58, 89, 196, 175, 27, 105, 79, 118, 14, 53, 253, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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