Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59be99a3dc2c027d1adb35ca871e15889aa2a468e8e0e959c8cd3a258456ee66

Tx prefix hash: bf4d1b3249a16b5ef80c90295598a0a688ec64f2dbd22d2ea52046c5289861c1
Tx public key: 0ba379104d97a03440e1df4252d4d7b2f7179a0db2a87702b1baf089c256811c
Timestamp: 1695740862 Timestamp [UCT]: 2023-09-26 15:07:42 Age [y:d:h:m:s]: 01:193:15:54:10
Block: 856636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399467 RingCT/type: yes/0
Extra: 010ba379104d97a03440e1df4252d4d7b2f7179a0db2a87702b1baf089c256811c02110000000533af99f4000000000000000000

1 output(s) for total of 0.890449660000 dcy

stealth address amount amount idx
00: dc823f071e9bdcf1be05574e7a8877d6b8b36e77bd43a5114bc34ccdda89cb68 0.890449660000 1310716 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": 856646, "vin": [ { "gen": { "height": 856636 } } ], "vout": [ { "amount": 890449660, "target": { "key": "dc823f071e9bdcf1be05574e7a8877d6b8b36e77bd43a5114bc34ccdda89cb68" } } ], "extra": [ 1, 11, 163, 121, 16, 77, 151, 160, 52, 64, 225, 223, 66, 82, 212, 215, 178, 247, 23, 154, 13, 178, 168, 119, 2, 177, 186, 240, 137, 194, 86, 129, 28, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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