Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d744059a3de1a733079270dca27eb32a0259f17d733141a54ba03e1eae26b8a5

Tx prefix hash: 0590fbe7ee38f68ba13fd94e368a217501fcd798b8b6ceac88fe462130a26f5e
Tx public key: 6d1d1c95c67650299ff9326dddb239c52d3c7e8c3d332ca60113c2923151239e
Timestamp: 1761440453 Timestamp [UTC]: 2025-10-26 01:00:53 Age [y:d:h:m:s]: 00:204:18:47:28
Block: 1398001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138910 RingCT/type: yes/0
Extra: 016d1d1c95c67650299ff9326dddb239c52d3c7e8c3d332ca60113c2923151239e0211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f22aaf1b8571639696cf1618bfd85261ab9888fd8609427005e63507c4666c94 0.000600000000 1886294 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": 1398011, "vin": [ { "gen": { "height": 1398001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f22aaf1b8571639696cf1618bfd85261ab9888fd8609427005e63507c4666c94" } } ], "extra": [ 1, 109, 29, 28, 149, 198, 118, 80, 41, 159, 249, 50, 109, 221, 178, 57, 197, 45, 60, 126, 140, 61, 51, 44, 166, 1, 19, 194, 146, 49, 81, 35, 158, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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: