Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 474c94fec6f545c88f8a0b4d6baf41f14e7e4ac23266ee3bda4f78a7dacceedf

Tx prefix hash: c0afbc17e0df82e0bf96265089463b0af777890d379ec71b38bbd687531a9ae2
Tx public key: acf42c7dbc780c6cd454a94e73fd841d2fd5d777c04570a1b6c53b0189bd457e
Timestamp: 1772684951 Timestamp [UTC]: 2026-03-05 04:29:11 Age [y:d:h:m:s]: 00:260:06:35:55
Block: 1490978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191663 RingCT/type: yes/0
Extra: 01acf42c7dbc780c6cd454a94e73fd841d2fd5d777c04570a1b6c53b0189bd457e021100000002da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc59e302f65e9d57d001bd963c7677417c1f65ba2bfd2100a768b2a2f0ab2210 0.000600000000 1980490 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": 1490988, "vin": [ { "gen": { "height": 1490978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc59e302f65e9d57d001bd963c7677417c1f65ba2bfd2100a768b2a2f0ab2210" } } ], "extra": [ 1, 172, 244, 44, 125, 188, 120, 12, 108, 212, 84, 169, 78, 115, 253, 132, 29, 47, 213, 215, 119, 192, 69, 112, 161, 182, 197, 59, 1, 137, 189, 69, 126, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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) | monero version: