Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae53ba3099a2fcd86a05e3b8ee3bdf28637e978c41a13dd9345c2e8f7d1143ad

Tx prefix hash: 53aa1e105cbc542066e71652c6f4190a65913b6e66775ab7281d1db5449ddb7d
Tx public key: 8d6e9bc0c2ec4d7a66c91186c2425b282915dd1ce42dc70eb66a8bc9489a370a
Timestamp: 1771089868 Timestamp [UTC]: 2026-02-14 17:24:28 Age [y:d:h:m:s]: 00:274:22:55:13
Block: 1477769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201993 RingCT/type: yes/0
Extra: 018d6e9bc0c2ec4d7a66c91186c2425b282915dd1ce42dc70eb66a8bc9489a370a021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 879869b8e37d5f825e931edab53b438fb95081891b0109ae6c0e67807871ea4a 0.000600000000 1967089 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": 1477779, "vin": [ { "gen": { "height": 1477769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879869b8e37d5f825e931edab53b438fb95081891b0109ae6c0e67807871ea4a" } } ], "extra": [ 1, 141, 110, 155, 192, 194, 236, 77, 122, 102, 201, 17, 134, 194, 66, 91, 40, 41, 21, 221, 28, 228, 45, 199, 14, 182, 106, 139, 201, 72, 154, 55, 10, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: