Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92d1eef3d5c9c96d35531eb55d28b10c32f19dd6daf67d50c885008f0e18c998

Tx prefix hash: aaeced756b9a2ae310b63f8700e571736b3fb20a0241ad6012d5449ea04503f4
Tx public key: 443ea832e82116f72ff6847003e9b5c357e64d851486038111df9bfa6cc14c4e
Timestamp: 1695405987 Timestamp [UCT]: 2023-09-22 18:06:27 Age [y:d:h:m:s]: 01:131:02:23:06
Block: 853850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354742 RingCT/type: yes/0
Extra: 01443ea832e82116f72ff6847003e9b5c357e64d851486038111df9bfa6cc14c4e02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.909579264000 dcy

stealth address amount amount idx
00: 627133673c9648c2fb25bb234d8bf4f6b3c10537e3e179d3caa41142f85ce866 0.909579264000 1307790 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": 853860, "vin": [ { "gen": { "height": 853850 } } ], "vout": [ { "amount": 909579264, "target": { "key": "627133673c9648c2fb25bb234d8bf4f6b3c10537e3e179d3caa41142f85ce866" } } ], "extra": [ 1, 68, 62, 168, 50, 232, 33, 22, 247, 47, 246, 132, 112, 3, 233, 181, 195, 87, 230, 77, 133, 20, 134, 3, 129, 17, 223, 155, 250, 108, 193, 76, 78, 2, 17, 0, 0, 0, 3, 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