Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba70a2ed8067563adfc6c41ccce0fa1cb426fe7d84e6a322868bf5835fe61eb5

Tx prefix hash: ff4c4e4c634ea5d443c032e17ce27ee03883c78c4c4f3e2093b672b4a2af1b85
Tx public key: 342b6edb0ca51efc30ec3fe28c809f40124bcc0f2a3b751b39661f17fc14917c
Timestamp: 1766299699 Timestamp [UCT]: 2025-12-21 06:48:19 Age [y:d:h:m:s]: 00:001:05:54:00
Block: 1438270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 888 RingCT/type: yes/0
Extra: 01342b6edb0ca51efc30ec3fe28c809f40124bcc0f2a3b751b39661f17fc14917c02110000000d7b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86febb43c8906c328df2ee35c82b1498479fd7aa1f890e8795c6b0d5fad765be 0.600000000000 1927087 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": 1438280, "vin": [ { "gen": { "height": 1438270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86febb43c8906c328df2ee35c82b1498479fd7aa1f890e8795c6b0d5fad765be" } } ], "extra": [ 1, 52, 43, 110, 219, 12, 165, 30, 252, 48, 236, 63, 226, 140, 128, 159, 64, 18, 75, 204, 15, 42, 59, 117, 27, 57, 102, 31, 23, 252, 20, 145, 124, 2, 17, 0, 0, 0, 13, 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