Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b9fdf632d3567283af77f351494a8f02edccea51f23dcd92e4a0121f9dfde1b

Tx prefix hash: c589041fd95651779acc1a2d5253690401d23f8edf327cf0b4053b0f3f7136b1
Tx public key: 676e6a6edfc3402882f60c820500672b3fc73c0d818b9cde983890bdf4f235e8
Timestamp: 1771982477 Timestamp [UTC]: 2026-02-25 01:21:17 Age [y:d:h:m:s]: 00:268:12:50:06
Block: 1485169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197573 RingCT/type: yes/0
Extra: 01676e6a6edfc3402882f60c820500672b3fc73c0d818b9cde983890bdf4f235e8021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d029e2d0f9e76f0ea97f76a8b48ed47988c09407f62396a0a33baec2803fdf87 0.000600000000 1974603 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": 1485179, "vin": [ { "gen": { "height": 1485169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d029e2d0f9e76f0ea97f76a8b48ed47988c09407f62396a0a33baec2803fdf87" } } ], "extra": [ 1, 103, 110, 106, 110, 223, 195, 64, 40, 130, 246, 12, 130, 5, 0, 103, 43, 63, 199, 60, 13, 129, 139, 156, 222, 152, 56, 144, 189, 244, 242, 53, 232, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: