Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b41a62aaebe045ccf1d2eccb93c1927cf05409e02f297ed00c5a2746f29d9c9

Tx prefix hash: cd8f39f882cc5df152ffa4db2d06b56be3f50e67e5a154dc38d1e7145eb84484
Tx public key: 61d748efd075e461af0c7d0c4a1cefc67393bf40f35aac75c35a2820edb94363
Timestamp: 1769480104 Timestamp [UTC]: 2026-01-27 02:15:04 Age [y:d:h:m:s]: 00:291:18:04:30
Block: 1464440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213934 RingCT/type: yes/0
Extra: 0161d748efd075e461af0c7d0c4a1cefc67393bf40f35aac75c35a2820edb94363021100000004215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 74509f5a7e11807de619f646c8b127253536638c85c3fbdb4b4f9d9b31c3ea15 0.000600000000 1953666 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": 1464450, "vin": [ { "gen": { "height": 1464440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74509f5a7e11807de619f646c8b127253536638c85c3fbdb4b4f9d9b31c3ea15" } } ], "extra": [ 1, 97, 215, 72, 239, 208, 117, 228, 97, 175, 12, 125, 12, 74, 28, 239, 198, 115, 147, 191, 64, 243, 90, 172, 117, 195, 90, 40, 32, 237, 185, 67, 99, 2, 17, 0, 0, 0, 4, 33, 91, 191, 137, 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: