Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6bc35f8441d96b85af64df6e1cb98099e14d298447bcfe75a73cf701b0346a1

Tx prefix hash: db73e583a61103ffb73e43d3d127b34b67bff4cb1dd4cac7e99da748e6959e78
Tx public key: b693f66ac4626b1ebbfc30e8ae4906ee61dcaafc4dc2e38a3fafd7c567f36445
Timestamp: 1753989558 Timestamp [UCT]: 2025-07-31 19:19:18 Age [y:d:h:m:s]: 00:022:00:13:01
Block: 1337531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14659 RingCT/type: yes/0
Extra: 01b693f66ac4626b1ebbfc30e8ae4906ee61dcaafc4dc2e38a3fafd7c567f36445021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e03c1741498246e2de14d3f5771ee6b9779cf8f354baa6197a13f220cc015c73 0.600000000000 1825336 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": 1337541, "vin": [ { "gen": { "height": 1337531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e03c1741498246e2de14d3f5771ee6b9779cf8f354baa6197a13f220cc015c73" } } ], "extra": [ 1, 182, 147, 246, 106, 196, 98, 107, 30, 187, 252, 48, 232, 174, 73, 6, 238, 97, 220, 170, 252, 77, 194, 227, 138, 63, 175, 215, 197, 103, 243, 100, 69, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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