Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620fa9c01db2572029b2e64f22a10973cf9a2e8c6da7caf0b03196fa73a6c638

Tx prefix hash: bc1674499d0e1c0cc9fe2f3c58481b88968c510885621ce18f4b79c73e2e0d58
Tx public key: dfcbbddf5eb6407c9476bb41273c85bee38d9950b39138d18d85d523e99a13bd
Timestamp: 1704345076 Timestamp [UTC]: 2024-01-04 05:11:16 Age [y:d:h:m:s]: 02:321:03:58:19
Block: 927774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754789 RingCT/type: yes/0
Extra: 01dfcbbddf5eb6407c9476bb41273c85bee38d9950b39138d18d85d523e99a13bd021100000008c5452960000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 35d0df4039e27112ee2836590fe4605394b4f4473ec2dbc545fe588201e06fe1 0.000600000000 1385610 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": 927784, "vin": [ { "gen": { "height": 927774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35d0df4039e27112ee2836590fe4605394b4f4473ec2dbc545fe588201e06fe1" } } ], "extra": [ 1, 223, 203, 189, 223, 94, 182, 64, 124, 148, 118, 187, 65, 39, 60, 133, 190, 227, 141, 153, 80, 179, 145, 56, 209, 141, 133, 213, 35, 233, 154, 19, 189, 2, 17, 0, 0, 0, 8, 197, 69, 41, 96, 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: