Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea5df1b1e6fe16c31dcddc647bc870d3a9e16f94750313ea1fbc6393fd0d1cde

Tx prefix hash: 4c6b16c705115df9c94f6f84b1a6dc4b4d31a56149e4bf183e6a8c1911172500
Tx public key: 18c8f726fe888d5af4f58a211ebd0013435046e7275f780651bd27c233db2175
Timestamp: 1696866580 Timestamp [UCT]: 2023-10-09 15:49:40 Age [y:d:h:m:s]: 01:141:14:27:41
Block: 865978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362194 RingCT/type: yes/0
Extra: 0118c8f726fe888d5af4f58a211ebd0013435046e7275f780651bd27c233db217502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.829192632000 dcy

stealth address amount amount idx
00: ba6173652ac0fdf76bede6aadd391130205ace119643fb580843af65f7cab654 0.829192632000 1320544 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": 865988, "vin": [ { "gen": { "height": 865978 } } ], "vout": [ { "amount": 829192632, "target": { "key": "ba6173652ac0fdf76bede6aadd391130205ace119643fb580843af65f7cab654" } } ], "extra": [ 1, 24, 200, 247, 38, 254, 136, 141, 90, 244, 245, 138, 33, 30, 189, 0, 19, 67, 80, 70, 231, 39, 95, 120, 6, 81, 189, 39, 194, 51, 219, 33, 117, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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