Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c83551c2ac898cec9a8396c077716162f76a5a5d87075dce8f1d8f61d6320d97

Tx prefix hash: 84270d440c8c1463dcf9644e3d41cb1d6e54689c27679b53655ca3d7cd7172db
Tx public key: 1f4b29fee826fc0f33dd6d76652d44b748e5bfb31d5fccc5ee45a991629d1c34
Timestamp: 1759300298 Timestamp [UCT]: 2025-10-01 06:31:38 Age [y:d:h:m:s]: 00:123:14:12:57
Block: 1380245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88336 RingCT/type: yes/0
Extra: 011f4b29fee826fc0f33dd6d76652d44b748e5bfb31d5fccc5ee45a991629d1c34021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d4f2370022d8ecf4054376f0836098d8c680b54ddf9f2c5562229ec0e890d79 0.600000000000 1868356 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": 1380255, "vin": [ { "gen": { "height": 1380245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d4f2370022d8ecf4054376f0836098d8c680b54ddf9f2c5562229ec0e890d79" } } ], "extra": [ 1, 31, 75, 41, 254, 232, 38, 252, 15, 51, 221, 109, 118, 101, 45, 68, 183, 72, 229, 191, 179, 29, 95, 204, 197, 238, 69, 169, 145, 98, 157, 28, 52, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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