Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49cb982beca3a239b3bee479c41eba4ec57af74e6eccf2d49647664ab8840dc

Tx prefix hash: 0e991f2295a783e460034d696833710e984be6fbd27b01129e9af5e748d7692b
Tx public key: 163ae5d53a9f84fd45155ff2b435cc71a86030c440a02e968a062c9160c87b45
Timestamp: 1772977006 Timestamp [UTC]: 2026-03-08 13:36:46 Age [y:d:h:m:s]: 00:251:09:17:09
Block: 1493401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185062 RingCT/type: yes/0
Extra: 01163ae5d53a9f84fd45155ff2b435cc71a86030c440a02e968a062c9160c87b45021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dbf35dfa24ea02179d8e461798acafa9de345a76f795364e86948fbc82eb9e51 0.000600000000 1982957 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": 1493411, "vin": [ { "gen": { "height": 1493401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf35dfa24ea02179d8e461798acafa9de345a76f795364e86948fbc82eb9e51" } } ], "extra": [ 1, 22, 58, 229, 213, 58, 159, 132, 253, 69, 21, 95, 242, 180, 53, 204, 113, 168, 96, 48, 196, 64, 160, 46, 150, 138, 6, 44, 145, 96, 200, 123, 69, 2, 17, 0, 0, 0, 7, 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: