Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85c336d0bef3a5e83688db5053bfc7821a11a2459eddcc2b578d986fd790572b

Tx prefix hash: 3b07c89b137d0f4be4e8d188cfffe3c044dbaa42fdc70418c3712a70f8a71ebc
Tx public key: 0e15dcc385b2784da1031d8b959509072f4c61c70a5d500746c1d9c7c8240a03
Timestamp: 1739383740 Timestamp [UTC]: 2025-02-12 18:09:00 Age [y:d:h:m:s]: 00:364:12:11:19
Block: 1217829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258206 RingCT/type: yes/0
Extra: 010e15dcc385b2784da1031d8b959509072f4c61c70a5d500746c1d9c7c8240a03021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd68eb3cd7df92d655a29a5d6444f0c84d2b49bf28e952e4c6b5e5464bc918e3 0.000600000000 1704644 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 dinastycoin-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": 1217839, "vin": [ { "gen": { "height": 1217829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd68eb3cd7df92d655a29a5d6444f0c84d2b49bf28e952e4c6b5e5464bc918e3" } } ], "extra": [ 1, 14, 21, 220, 195, 133, 178, 120, 77, 161, 3, 29, 139, 149, 149, 9, 7, 47, 76, 97, 199, 10, 93, 80, 7, 70, 193, 217, 199, 200, 36, 10, 3, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369