Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 672fa3a315432e31435e18f009457d22a47a4be3007639012a55372a8882c5c7

Tx prefix hash: d22bf1a0e3098afc5b418c7a5a381c912911e6e428f163b9c7f350802ce9cf91
Tx public key: dd2dd61186630e7d74cdfde8146c0e80de3f959e9461b23433eab9adca62a4e3
Timestamp: 1748399713 Timestamp [UCT]: 2025-05-28 02:35:13 Age [y:d:h:m:s]: 00:171:16:23:46
Block: 1292464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120390 RingCT/type: yes/0
Extra: 01dd2dd61186630e7d74cdfde8146c0e80de3f959e9461b23433eab9adca62a4e302110000000586ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b119d76d6bf82d19f8a1897d8e8a717d711a69e14346028183041596ca71a4ba 0.600000000000 1779935 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": 1292474, "vin": [ { "gen": { "height": 1292464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b119d76d6bf82d19f8a1897d8e8a717d711a69e14346028183041596ca71a4ba" } } ], "extra": [ 1, 221, 45, 214, 17, 134, 99, 14, 125, 116, 205, 253, 232, 20, 108, 14, 128, 222, 63, 149, 158, 148, 97, 178, 52, 51, 234, 185, 173, 202, 98, 164, 227, 2, 17, 0, 0, 0, 5, 134, 174, 47, 13, 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