Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a32200e7e5ac3c059e409c0677ae4d2d4f2f0753c06c8ad3f795ac7a99383e

Tx prefix hash: 8dff0c2f7ce6f60ddc149baa238ac4892737af131a479e0e89a654f23e1cf2d6
Tx public key: 2f28cc5adec706042aa664aa5278abdf917577db6a0337e0175cc0fb47f8d6e4
Timestamp: 1766220476 Timestamp [UCT]: 2025-12-20 08:47:56 Age [y:d:h:m:s]: 00:001:12:02:51
Block: 1437610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1067 RingCT/type: yes/0
Extra: 012f28cc5adec706042aa664aa5278abdf917577db6a0337e0175cc0fb47f8d6e402110000000c7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94f22f1f2103191f81fd71873a86f937b48d97c5def591dc719ca08ee5e4b3e 0.600000000000 1926419 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": 1437620, "vin": [ { "gen": { "height": 1437610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94f22f1f2103191f81fd71873a86f937b48d97c5def591dc719ca08ee5e4b3e" } } ], "extra": [ 1, 47, 40, 204, 90, 222, 199, 6, 4, 42, 166, 100, 170, 82, 120, 171, 223, 145, 117, 119, 219, 106, 3, 55, 224, 23, 92, 192, 251, 71, 248, 214, 228, 2, 17, 0, 0, 0, 12, 123, 30, 81, 172, 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