Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c8d08f513a9711b2c3b9e8d1507c890bc50b7933d9bd4328b314dc0bffb8753

Tx prefix hash: 56f3404c7cad509f757025a18422208386dd0347ca82bcfe1045b4b19f8eb5b4
Tx public key: 594ff35fd1b2a50542f810886510eaef165b2f292255226b61969a4b27a090fc
Timestamp: 1697359501 Timestamp [UCT]: 2023-10-15 08:45:01 Age [y:d:h:m:s]: 01:132:00:41:23
Block: 870064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355340 RingCT/type: yes/0
Extra: 01594ff35fd1b2a50542f810886510eaef165b2f292255226b61969a4b27a090fc021100000010faf35c9c000000000000000000

1 output(s) for total of 0.803742280000 dcy

stealth address amount amount idx
00: ae5efd9584236ba43299a7e9c7694e04e97b67dd3fc76aa92259b8a16808803e 0.803742280000 1324937 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": 870074, "vin": [ { "gen": { "height": 870064 } } ], "vout": [ { "amount": 803742280, "target": { "key": "ae5efd9584236ba43299a7e9c7694e04e97b67dd3fc76aa92259b8a16808803e" } } ], "extra": [ 1, 89, 79, 243, 95, 209, 178, 165, 5, 66, 248, 16, 136, 101, 16, 234, 239, 22, 91, 47, 41, 34, 85, 34, 107, 97, 150, 154, 75, 39, 160, 144, 252, 2, 17, 0, 0, 0, 16, 250, 243, 92, 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