Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e567680d415f2b38c45af08f4f93b5bb7f3df10f4af9bd4d06ad3c48d9897ff

Tx prefix hash: 701fd12f5ad207a64e5d60fd75d76c40cc2500ae53c0b04fd11314c501186614
Tx public key: d410da0c70eaf2bdae5ca8aa920fc794c0998b5d0052290d7858c2f620d2a5cc
Timestamp: 1733757272 Timestamp [UCT]: 2024-12-09 15:14:32 Age [y:d:h:m:s]: 00:191:12:28:54
Block: 1171516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136565 RingCT/type: yes/0
Extra: 01d410da0c70eaf2bdae5ca8aa920fc794c0998b5d0052290d7858c2f620d2a5cc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0506a8b22ca613e08372b7b329e0211df1efe3b9f3a6434ad421f276e1f7f834 0.600000000000 1657285 of 15

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": 1171526, "vin": [ { "gen": { "height": 1171516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0506a8b22ca613e08372b7b329e0211df1efe3b9f3a6434ad421f276e1f7f834" } } ], "extra": [ 1, 212, 16, 218, 12, 112, 234, 242, 189, 174, 92, 168, 170, 146, 15, 199, 148, 192, 153, 139, 93, 0, 82, 41, 13, 120, 88, 194, 246, 32, 210, 165, 204, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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