Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc53002499a0b92bc48ced86e147d44dd2e727473c37342ee04e459eb93c30c

Tx prefix hash: 30718c14cf69606a902705ac985b98bcecd6da79558779340e55c807c6bbd173
Tx public key: 671f2b99f1ebbb0d00b62c9931182bfac8e5e8330aaff45efb4e62ee40593efe
Timestamp: 1757291539 Timestamp [UTC]: 2025-09-08 00:32:19 Age [y:d:h:m:s]: 01:071:23:42:45
Block: 1363707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317792 RingCT/type: yes/0
Extra: 01671f2b99f1ebbb0d00b62c9931182bfac8e5e8330aaff45efb4e62ee40593efe021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c79360306c2e124d2e215c5e1e8e0f3cd6597d80c19fde55ce405b87c31f66e 0.000600000000 1851746 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": 1363717, "vin": [ { "gen": { "height": 1363707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c79360306c2e124d2e215c5e1e8e0f3cd6597d80c19fde55ce405b87c31f66e" } } ], "extra": [ 1, 103, 31, 43, 153, 241, 235, 187, 13, 0, 182, 44, 153, 49, 24, 43, 250, 200, 229, 232, 51, 10, 175, 244, 94, 251, 78, 98, 238, 64, 89, 62, 254, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: