Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1d8e336e9c74f76eee8cef120b4daba55d20b0c7cbcd73478f91598da60c06b

Tx prefix hash: 29ae5c05dc24e0ca36e075011bef3452386a88146993d3e45c2cbfd0642bbd9e
Tx public key: 6f9ed60b6d1923e957a9a5d45662e6716986f826720283809c470cb9525db297
Timestamp: 1743445865 Timestamp [UTC]: 2025-03-31 18:31:05 Age [y:d:h:m:s]: 01:233:01:16:18
Block: 1251443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430671 RingCT/type: yes/0
Extra: 016f9ed60b6d1923e957a9a5d45662e6716986f826720283809c470cb9525db29702110000000e703241eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 734f3110da9f62ed4d5a1de7bd116be11611f00ae1091362415d32401174fad1 0.000600000000 1738510 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": 1251453, "vin": [ { "gen": { "height": 1251443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "734f3110da9f62ed4d5a1de7bd116be11611f00ae1091362415d32401174fad1" } } ], "extra": [ 1, 111, 158, 214, 11, 109, 25, 35, 233, 87, 169, 165, 212, 86, 98, 230, 113, 105, 134, 248, 38, 114, 2, 131, 128, 156, 71, 12, 185, 82, 93, 178, 151, 2, 17, 0, 0, 0, 14, 112, 50, 65, 235, 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: