Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f09415106b466c13dea5c6aa1763bfbdaf85a7a43fd9fce89bfcff81f9e9c7

Tx prefix hash: 67830bb84b15918df81e32430250acc4cd737d78e1c0ebf589b7a179f8a58b81
Tx public key: b7cc22cbcdafd94c15963ab476fbf1f51542de9e879f263617d49f4c1249c210
Timestamp: 1744569690 Timestamp [UCT]: 2025-04-13 18:41:30 Age [y:d:h:m:s]: 00:030:21:59:54
Block: 1260746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22127 RingCT/type: yes/0
Extra: 01b7cc22cbcdafd94c15963ab476fbf1f51542de9e879f263617d49f4c1249c2100211000000086c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963c5f482c29fedb91e5c36703347ce7961c4eb17f2b25a5ca58093d8650bfa1 0.600000000000 1747907 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": 1260756, "vin": [ { "gen": { "height": 1260746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963c5f482c29fedb91e5c36703347ce7961c4eb17f2b25a5ca58093d8650bfa1" } } ], "extra": [ 1, 183, 204, 34, 203, 205, 175, 217, 76, 21, 150, 58, 180, 118, 251, 241, 245, 21, 66, 222, 158, 135, 159, 38, 54, 23, 212, 159, 76, 18, 73, 194, 16, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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