Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273d2a4c79f8ab770bd8d2e079894b0d1185b4a2d3c082feb3de23d47bbf69c5

Tx prefix hash: 324ab60491ed4b47d83fb6b521a245727cc34ca1259da1a80d6ec847c58d7fc7
Tx public key: 80090adc9444eedf3ed596408943b572e15845018c73ad9d2fed2fe9e9102082
Timestamp: 1772539086 Timestamp [UTC]: 2026-03-03 11:58:06 Age [y:d:h:m:s]: 00:261:18:04:16
Block: 1489761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192697 RingCT/type: yes/0
Extra: 0180090adc9444eedf3ed596408943b572e15845018c73ad9d2fed2fe9e9102082021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d9a0ec323d9991bae6de6c52a50f15a9d2e23588557de95f541fe18c910f209 0.000600000000 1979259 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": 1489771, "vin": [ { "gen": { "height": 1489761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9a0ec323d9991bae6de6c52a50f15a9d2e23588557de95f541fe18c910f209" } } ], "extra": [ 1, 128, 9, 10, 220, 148, 68, 238, 223, 62, 213, 150, 64, 137, 67, 181, 114, 225, 88, 69, 1, 140, 115, 173, 157, 47, 237, 47, 233, 233, 16, 32, 130, 2, 17, 0, 0, 0, 3, 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: